The Debug menu contains items relating to debugging files or programs. This section discusses the items which may not be familiar. The availability of items in this menu is determined by the debugger being used. If a feature is not supported by the debugger the menu item will remain disabled.
This option will start the program/file in the debugger. The debugger will be suspended when it reaches any specified breakpoints or the end of the program. You can use the Break item in the Debug menu to attempt to suspend the program within debugger while it is busy.
This option will start the program/file in the debugger but will be suspended at the first executable line. This line will then be highlighted in the code editor if possible.
Selecting this option will prompt you for the ID of the existing process you wish to debug. After entering a valid process ID the debugger is started with instructions to connect to the specified process. You can use the Break item in the Debug menu to attempt to suspend the program within debugger while it is busy.
This will continue the execution of the program/file within the debugger.
This will restart the debugger keeping existing breakpoints.
This will stop and exit the debugger.
This will attempt to suspend the execution of the program/file within the debugger, locating the current statement and highlighting this within the code editor. In the event the current statement does not identify a filename and line number, the call stack is displayed.
This will simply close the active TELNET session, which in turn should terminate the debugger and target on the server. This option should be used with caution and only in cases where Stop Debugging fails.
This will attempt to step into the sub-procedure/function located on the current statement in the code editor. If the current statement does not identify a sub-procedure/function, this may fail or the debugger may perform a Step Over (depending upon the debugger).
This will attempt to execute the code represented by the current statement in the code editor and break execution at the next statement in the current file. If there isn't a next statement in the current file, this may fail or the debugger may highlight the next executable statement (depending upon the debugger).
This will attempt to set a temporary breakpoint at the statement on which the cursor is located in the code editor and then continue program execution.
This will attempt to move the current statement to the statement on which the cursor is located in the code editor without executing code in between. This should be used with caution as it may leave the debug target in an unusable state.
This will display the current call hierarchy for the current statement.
This will display the contents of all local variables (if applicable to the programming language) in their native format.
This will insert a new breakpoint in the debugger at the line on which the cursor is located in the code editor. If the current line represents an existing breakpoint, that breakpoint is deleted.
This will display a dialog box in which you can edit, remove or add to the existing breakpoints specified for the current debug session.
This will highlight the debuggerÆs current statement in the code editor, opening any necessary files.
This will display the Quick Watch dialog box. This evaluates the currently selected text or the keyword at the cursor in the code editor. The results of the evaluation will then be displayed in their native format.